home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Grab Bag
/
Shareware Grab Bag.iso
/
081
/
ommm_107.arc
/
OMMM.NEW
< prev
Wrap
Text File
|
1987-09-16
|
11KB
|
245 lines
This oMMM has some new routing verbs and some that are translations of old
routing verbs. The following translations have to be made:
DoCrash -> DoCM
ArcTo -> ArcDirect
**NEW** -> OneDirect
**NEW** -> UnDirect
Direct -> NormDirect
Hold -> ArcHold
Crash -> ArcCM
OneCrash -> OneCM
UnCrash -> UnCM
NormCrash-> NormCM
Here is what each verb does:
SCHED..... Starts a schedule. All oMMM statements between
this statement and the next SCHED statement will
be executed if the schedule tag matches the one
given on the command line. tag is a character
that can be in upper or lower case.
SYNTAX: Sched tag
LEAVE..... Mark all packets to the listed nodes such that
Opus will not attempt to send them. Use the -z
command line option of oMMM to make the packets
be recognized by Opus for future sending. Use
this option with extreme care!
SYNTAX: Leave destinations
ACTUAL: xxxxyyyy.?UT->xxxxyyyy.N?T
xxxxyyyy.?LO->xxxxyyyy.N?O
SEND...... If a node in the destination list has a packet
that has been marked as a "do not send" packet
by using LEAVE, then make it so that the packet
can once again be sent.
SYNTAX: Send destinations
ACTUAL: xxxxyyyy.N?T->xxxxyyyy.?UT
xxxxyyyy.N?O->xxxxyyyy.?LO
EXAMPLE to do local schedule with some
extra nodes:
; First mark all nodes as no-send
Leave All
; Now send to our net and list
Send Ournet 132/101 124/108
DOCM...... If a node in the destination list has a packet
that has been marked as a "do not send" packet
by using LEAVE, and the packet is a CM type of
packet, then that packet is marked for sending.
SYNTAX: DoCM
ACTUAL: xxxxyyyy.NCT->xxxxyyyy.CUT
xxxxyyyy.NCO->xxxxyyyy.CLO
POLL...... This creates a dummy .FLO file if there are no
files existing for the given node that are not
on hold. If there are files in the holding area
which are going to the given node, and they are
not on hold, then the POLL statement will do
nothing.
SYNTAX: Poll destinations
ACTUAL: If no xxxxyyyy.[FCD]LO then
creates xxxxyyyy.FLO
ROUTE..... Host route any remaing .OUT packets. Any
packets remaining in the outbound area with an
extension of .OUT will be routed to the host
for the network. This should normally be the
last statement in the oMMM control file (other
than Poll statements - if a Poll statement
precedes the Route statement, then it will create
a .OUT file which will then be host routed - not
the behavior that would normally be expected) for
any given schedule.
SYNTAX: Route
ACTUAL: xxxxyyyy.OUT->xxxx0000.OUT
[This ] UNROUTE... Unbundles any .OUT files that are addressed to
[option ] nodes of the form net/0. This operation sometimes
[is ] will take a while to perform if a lot of host
[not ] routing has been done.
[yet ]
[available] SYNTAX: UnRoute
ARCDIRECT. Send as direct mail during pre-set schedules.
This command actually ARC's up the packets just
like ARCmail would do, so you must be sure that
the receiving system either has ARCmail that runs
at regular intervals, or is running Opus 1.00 or
higher.
SYNTAX: ArcDirect destination [routelist]
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.DLO
with an ARCmail file listed
EXAMPLES: ArcDirect 124/0 124/ALL
ArcDirect 135/1
ONEDIRECT. This call is identical to the above call except
that all nodes listed have the packets ARCmailed
individually. This allows statements to be used
in a program like XlatList<tm> that will send to
a list of nodes.
SYNTAX: OneDirect destinations
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.DLO
with an ARCmail file listed
UNDIRECT.. Any packets to the nodes in the list that are
marked as DIRECT are marked normal.
SYNTAX: UnDirect destinations
ACTUAL: xxxxyyyy.DUT->xxxxyyyy.OUT
xxxxyyyy.DLO->xxxxyyyy.FLO
NORMDIRECT Any packets to the nodes in the list are sent
as DIRECT type packets that are compatible with
other <tm> software. This basically means that
the packet is not ARC'd.
SYNTAX: NormDirect destinations
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.DUT
xxxxyyyy.FLO->xxxxyyyy.DLO
ARCHOLD... Prepare an ARCmail archive, but do not allow an
outgoing phone call. The archive will be held for the
other system to pickup. This has the same comment
as the ARCTO statement - ie the receiver must have
some way to unARC the packets.
SYNTAX: ArcHold destination [routelist]
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.HLO
with an ARCmail file listed
ONEHOLD... This call is identical to the above call except
that all nodes listed have the packets ARCmailed
individually. This allows statements to be used
in a program like XlatList<tm> that will send to
a list of nodes.
SYNTAX: OneHold destinations
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.HLO
with an ARCmail file listed
UNHOLD.... Any packets to the nodes in the list that are
marked as HOLD are marked normal.
SYNTAX: UnHold destinations
ACTUAL: xxxxyyyy.HUT->xxxxyyyy.OUT
xxxxyyyy.HLO->xxxxyyyy.FLO
NORMHOLD.. Any packets to the nodes in the list are sent
as HOLD type packets that are compatible with
other <tm> software. This basically means that
the packet is not ARC'd.
SYNTAX: NormHold destinations
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.HUT
xxxxyyyy.FLO->xxxxyyyy.HLO
ARCCM..... Send to a system which supports continuous
mail. Such systems include other Opus systems
and Seadog (v4.00). Again, the receiver must have
a way to unARC the packets.
In the Opus control file, you have some control
over continuous mail. See the part dealing with
"Matrix send CM only".
SYNTAX: ArcCM destination [routelist]
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.CLO
with an ARCmail file listed
ONECM..... This call is identical to the above call except
that all nodes listed have the packets ARCmailed
individually. This allows statements to be used
in a program like XlatList<tm> that will send to
a list of nodes.
SYNTAX: OneCM destinations
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.CLO
with an ARCmail file listed
UNCM...... Any packets to the nodes in the list that are
marked as CM are marked normal.
SYNTAX: UnCM destinations
ACTUAL: xxxxyyyy.CUT->xxxxyyyy.OUT
xxxxyyyy.CLO->xxxxyyyy.FLO
NORMCM.... Any .OUT packets to the nodes in the list are sent
as CM type packets that are compatible with
other <tm> software. This basically means that
the packet is not ARC'd.
SYNTAX: NormCM destinations
ACTUAL: xxxxyyyy.OUT->xxxxyyyy.CUT
xxxxyyyy.FLO->xxxxyyyy.CLO